docs: use one Closes keyword per issue in PR template#72
Merged
Conversation
GitHub may silently skip issues when multiple are comma-separated on one line. Use separate lines to ensure all issues close on merge. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
subotic
force-pushed
the
feat/batch-cli-improvements
branch
from
f09b2c9 to
9b28daa
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #71
Motivation
PR #69 used
Closes #39, #40, #41, #43, ...on one line. GitHub closed mostbut silently skipped #43, #49, and #50. The comma-separated format is unreliable.
Summary
docs/commit-conventions.mdto show oneClosesper lineTest Plan
🤖 Generated with Claude Code